support for spark.sql.datetime.java8API.enabled #125
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Motivation: when using connector with thrift server, any queries on data containing date/time types are crashing. It's caused by thrift server enabling `spark.sql.datetime.java8API.enabled` flag for all of its sessions. Supported JSR-310 types which are already supported by Spark SQL: - LocalDate - LocalDateTime - Instant Other types are causing Encoder to fail, so they won't work even if taken into account. As `spark.sql.datetime.java8API.enabled` is disabled by default, it shouldn't cause compatibility issues.
rozza
requested review from
katcharov and
rozza
and removed request for
katcharov
rozza
added a commit
to rozza/mongo-spark
that referenced
this pull request
Dec 3, 2025
Motivation: when using connector with thrift server, any queries on data containing date/time types are crashing. It's caused by thrift server enabling `spark.sql.datetime.java8API.enabled` flag for all of its sessions. Supported JSR-310 types which are already supported by Spark SQL: - LocalDate - LocalDateTime - Instant Other types are causing Encoder to fail, so they won't work even if taken into account. As `spark.sql.datetime.java8API.enabled` is disabled by default, it shouldn't cause compatibility issues. Adds support for the Spark 3.4 TimeTimestampNTZType SPARK-453 Original PR: mongodb#125 --------- Co-authored-by: Ross Lawley <[email protected]>
Member
|
Closed in favor of: #144 - which takes this PR as a base |
rozza
added a commit
to rozza/mongo-spark
that referenced
this pull request
Dec 3, 2025
Motivation: when using connector with thrift server, any queries on data containing date/time types are crashing. It's caused by thrift server enabling `spark.sql.datetime.java8API.enabled` flag for all of its sessions. Supported JSR-310 types which are already supported by Spark SQL: - LocalDate - LocalDateTime - Instant Other types are causing Encoder to fail, so they won't work even if taken into account. As `spark.sql.datetime.java8API.enabled` is disabled by default, it shouldn't cause compatibility issues. Adds support for the Spark 3.4 TimeTimestampNTZType SPARK-453 Original PR: mongodb#125 --------- Co-authored-by: Ross Lawley <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation: when using connector with thrift server, any queries on data containing date/time types are crashing. It's caused by thrift server enabling
spark.sql.datetime.java8API.enabledflag for all of its sessions.Supported JSR-310 types which are already supported by Spark SQL:
As
spark.sql.datetime.java8API.enabledis disabled by default, it shouldn't cause compatibility issues.SPARK-453